Skip to content

fix(cloudformation): handle telemetry setting in upgrade path case where setting is not registered#8343

Merged
laileni-aws merged 8 commits intoaws:masterfrom
atennak1:fix/settings
Nov 21, 2025
Merged

fix(cloudformation): handle telemetry setting in upgrade path case where setting is not registered#8343
laileni-aws merged 8 commits intoaws:masterfrom
atennak1:fix/settings

Conversation

@atennak1
Copy link
Contributor

Problem

When the extension is upgraded and user does not do a full restart, it is possible for new cloudformation telemetry setting to not be registered yet, resulting in error trying to save it.

Solution

Skip the save and do it the next time the extension starts.


  • Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.
  • Your code changes must meet the guidelines in CONTRIBUTING.md.
  • License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

@atennak1 atennak1 requested a review from a team as a code owner November 21, 2025 01:45
@github-actions
Copy link

  • This pull request implements a feat or fix, so it must include a changelog entry (unless the fix is for an unreleased feature). Review the changelog guidelines.
    • Note: beta or "experiment" features that have active users should announce fixes in the changelog.
    • If this is not a feature or fix, use an appropriate type from the title guidelines. For example, telemetry-only changes should use the telemetry type.

@laileni-aws
Copy link
Contributor

/retryBuilds

@laileni-aws laileni-aws merged commit 6bd7267 into aws:master Nov 21, 2025
30 of 31 checks passed
aws-ajangg pushed a commit to aws-ajangg/aws-toolkit-vscode that referenced this pull request Jan 15, 2026
…ere setting is not registered (aws#8343)

## Problem
When the extension is upgraded and user does not do a full restart, it
is possible for new cloudformation telemetry setting to not be
registered yet, resulting in error trying to save it.

## Solution
Skip the save and do it the next time the extension starts.

---

- Treat all work as PUBLIC. Private `feature/x` branches will not be
squash-merged at release time.
- Your code changes must meet the guidelines in
[CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

---------

Co-authored-by: Akila Tennakoon <tennakoo@amazon.com>
Co-authored-by: manodnyab <66754471+manodnyab@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants